[Improve] Make guided agent interactions reliable - #2475

​Created by Roomote. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

• Add optional integration discovery to setup: ask about named document, analytics/monitoring, and project-tracking tools; exact-match supported connectors; reuse secure configuration dialogs; and allow users to skip or reorder the funnel without blocking setup completion.
• Keep guided questions and human choices in chronological Session history, attribute answers to the responder, suppress duplicate successful request_user_input tool rows only when a card exists, keep failed tool calls visible, and leave the composer available beside optional questions.
• Make structured answers replay-safe: canonical option IDs remain persisted while visible history shows labels; repeated or contending submissions use the persisted winner; deterministic durable continuation recovers if the original process dies after saving an answer.
• Durably resume setup turns, coalesce setup changes into one deterministic model turn, complete zero-match discovery server-side, and keep the designed reorderable funnel in the prompt while code owns authorization, readiness, persistence, and launch invariants.
• Share effective integration status across setup and Settings, refresh Fast capabilities after connection/configuration changes, and harden Discord/shared communication actions with guarded cleanup, resume rebinding, stronger callback tokens, and reply-target authorization.

This standalone draft contains and supersedes the relevant implementation from PR #2402. It does not depend on #2402 landing; #2402 remains open and unchanged.

The source branch itself is based directly on main. The PR base still needs to be retargeted to main: the provider-neutral update operation created duplicate draft #2473 instead of changing #2470, and the current task API exposes no retarget or close operation. Do not merge either draft until #2470 is retargeted and #2473 is closed.

Why this change was made

Setup Sessions could require several attempts because tool plumbing appeared before cards, human choices disappeared or showed internal values, asynchronous setup events produced incoherent ordering, and a saved answer could be stranded before model continuation. Connection state and chat interaction guarantees also differed across surfaces.

Impact

Guided interactions now read as one coherent conversation and remain correct across reloads, retries, concurrent submissions, and supported chat adapters. The prompt keeps a deliberately designed setup progression while users can skip or reorder optional steps and the backend enforces reliable conversation-wide behavior.

Validation and local testing

Passed against the standalone main ancestry:

• pnpm check-types:fast
• pnpm lint:fast
• pnpm knip (only the existing Mint configuration hint)
• 152 focused web client tests
• 41 focused web server tests
• 385 focused cloud-agent tests
• 119 focused SDK tests
• 32 focused communication/API tests
• 28 focused shared-type tests
• Commit formatting hooks and full pre-push gates

Branch ancestry is exactly four commits ahead of origin/main: the two setup-discovery commits, the guided-interactions implementation, and the review-fix commit. Its merge base equals the current origin/main; unrelated post-release develop commits are excluded.

The preview browser was unauthenticated and further login/browser verification was explicitly canceled. No authenticated browser result, screenshot, ordinary-session live smoke, or external OAuth completion is claimed.

Local verification:

1. git fetch origin
2. git switch feature/guided-interactions-2hkp457mhpgoz
3. mise install && pnpm install
4. Start the normal stack with pnpm dev.
5. Open a setup or ordinary Session and verify: a successful question card has no duplicate tool row; a failed input request keeps its failure row; optional questions leave the composer available; submitted option labels remain in chronological human-attributed history after reload; setup can skip or reorder integration discovery; a zero-match discovery does not strand readiness events.
6. With a non-production integration test account, connect a supported provider and return to the Session to verify status/tool availability refresh. Do not use production credentials.